JCSM Shareware Collection 1993 November

home *** CD-ROM | disk | FTP | other *** search

/ JCSM Shareware Collection 1993 November / JCSM Shareware Collection - 1993-11.iso / cl980 / datapln3.lzh / A9.#@# / HELP.BAS

Wrap

BASIC Source File | 1993-05-24 | 111.7 KB | 2,624 lines

***************************************************************************** Ä"CLEARANCE(tm)" (c) COPYRIGHT 1983-1993 by DATA-PLANE INC. ALL RIGHTS RESERVED ÄCOPYRIGHT NOTICE DATA-PLANE INCORPORATED makes this package available for use on a single computer only. It is unlawful to copy any portion of this software package onto any medium for any purpose whatsoever other than backup. It is unlawful to give away or resell copies of any part of this package. Any unauthorized distribution of this product deprives DATA-PLANE of their deserved royalties. For use on multiple computers please contact DATA-PLANE INCORPORATED to make such arrangements. ÄWARNING Use of any portion or part thereof of the programs and/or the data-bases contained herein in any commercial application is strictly prohibited without the express written consent of Data-Plane Inc. ÄWARRANTY DATA-PLANE INCORPORATED makes no warranties expressed or implied as to the fitness of this software product for any particular purpose. Users are referred to the manufacturer's and manuals of the aircraft which they intend to fly and to current Maps & Charts to ascertain the correctness and accuracy of any solution. DATA-PLANE INC. makes no warranties as to the currency or accuracy of the Data-Base. However DATA-PLANE INC will exert its best efforts to maintain and up-date said Data-Base. User's shall be supplied up-dated Data-Bases under the terms and conditions of a separate maintenance Agreement. ÄSUBSCRIPTIONS In compliance with Data-Plane's liability to keep users current purchasers will automatically be put on the sub-scription list for up-dates of any module(s) which they have received; and the purchaser hereby agrees to accept said up-dates. These Subscriptions are good until cancelled; a courtesy 30 day written notice required. .................................................................. . THE NAVIGATIONAL AID (NAVAID) DATA HAS BEEN PRODUCED . . BY THE NATIONAL OCEAN SERVICE (NOS) IN BEHALF OF . . THE FEDERAL AVIATION ADMINISTRATION (FAA). THE DATA . . CONTAINED HEREWITH IS SUBJECT TO THE EXPIRATION . . EFFECTIVE AND CREATION DATES OF THE NOS CALENDAR. EACH . . 56 DAY ISSUE SUPERCEDES AND REPLACES THE PREVIOUS 56 DAY . . ISSUANCE. USERS ARE URGED AS COMMON PRACTICE TO CHECK . . THE APPROPRIATE NOTICES TO AIRMEN (NOTAMS) FOR INFORMA- . . TION CHANGES. DATA-PLANE INC ASSUMES NO RESPONSIBILITY . . FOR MODIFICATION OR APPLICATION OF THE DATA BY ANY USER. . .................................................................. Users are urged to contact the FSS to confirm & verify the correctness of the Flight Plans generated by the CLEARANCE computer programs. First Printing January 1986 Second Printing September 1986 Third Printing July 1987 Fourth Printing October 1987 Fifth Printing January 1988 Sixth Printing May 1988 Seventh Printing July 1988 Eighth Printing September 1988 Nineth Printing July 1989 Tenth Printing October 1989 Eleventh Printing January 1990 Twelveth Printing March 1990 Thirteenth Printing December 1990 Fourteenth Printing February 1991 Fifteenth Printing September 1992 . Printed in U.S.A. by DATA-PLANE INCORPORATED 330 S.W.43rd Street Renton Washington 98055 1-(800)-323-8063 USA / Canada î ÄFOREWORD This is a system of programs all interfacing through the MAIN MENU. The CLEARANCE Flight Planner is based on a digitized data-base faithful to the Charts & Maps published by NOS. The design philosophy endeavors to automate the entire procedure with as little Pilot input as possible. At the foundation of this approach is an algorithm which periodically fetches the Winds Aloft from a central Weather Base via a telephone modem. Such an algorithm has been perfected using the facilities of ACCU-WEATHER INC and GLOBAL WEATHER DYNAMICS INC and WORLD WEATHER WATCH OF TORONTO (TABS) and DUAT. The system is designed to be used with very little instruction. Experience has shown that after a short period of experimentation the average Pilot will master & enjoy the system. There is a set of DOS command line instructions which allow the user to combine several flight planning functions into one powerful easy to understand command. The Clearance flight planning system will also do everything on schedule while you sleep. There are six (6) different methods of flight plans a full Weight & Balance performance profile Airport Directory(s) a set of Pooled stored Flight Plans ATC preferred plans AIRWAY AUTO-ROUTING GRAPHICS a Professional Pilot Log Book Runway graphics DUAT interface....and graphic screen dumps for hard copy. Also a system awake feature which causes the system to enter into modem operations at an appointed moment. This version allows unlimited total flexibility. Plans may be composed of any combination of the the following segment types: _ DIRECT / AIRWAY / RNAV / DME FIXES / LAT-LON / INTERSECTIONS / AIRPORTS These types may appear and mix in any order in the flight plan......and may be freely edited.......with the full screen editing features. If we don't have an airport or fix....which you need for your flying...let us know and we'll include it. We'll custom design the database(s) to suit your flying needs. ÄAIRLINE STANDARDS Clearance is programmed to Airline standards; with an Airline technique of inserting RNAV way-points into any Flight Plan string. The Clearance Flight Planning system will out-perform anything else available .....and we're making it better! It is a very powerful PC based Flight Planner. The data-bases are incomparable.....and expanding each cycle. It is said that the system is well worth the price just for the databases all of which can be accessed and printed. Intuition is not required with this system. ÄDUAT If you become a DUAT user.....you will soon find out that this Flight Planner is an excellent and necessary pre-DUAT exercise. Weather briefings using Data-Plane software are FAA Sanctioned! ÄMANUAL * To Print the Addendum......d:\> FBOHELP ÄMENUS In the discussions which follow there are several major menus: _ Menu Selection(s) ______________________ __________________________ 1) MAIN [F1]........[F10] 2) AUDIT <A>.........<z> 3) FLIGHT PLAN <A>.........<S> 4) WINDS ALOFT <A>.........<z> (Modem download) 5) WINDS ALOFT <A>.........<z> (Manual entries) 6) WEATHER BRIEF <A>.........<z> 7) DUAT <A>.........<Z> 8) AIRPORT FACILITIES State 9) AVAILABLE AIRCRAFT <Type> Access to these menus is via the Main Menu....or directly from the DOS command line....instructions shall be displayed on the screen after each session. ÄDEFINITIONS . d: = any disc h: = any hard drive C: = C drive E: = E drive..etc. . tbd = to be determined. {..}= Optional Parameter. . St: = Start/From De: = Destination/To . xxxxx = Border crossing. FR = Fuel Remaining (lbs) . {target} = drive to load VR = Vertical Rate Required (ft/min) î ÄSUB-DIRECTORIES * Two sub-directories are created automatically during the install procedure: _ TAKE-OFF.DIR & TAKE-OFF.W&B * SIX Batch files are placed in your root directory: _ FBOZ/FBO/FBO$/FBO!/FBOHELP/MODEL..these may be moved to any other directory _ or renamed. _ e.g. C:\> COPY FBO*.BAT <sub-directory> _ Move all....or none & all must reside on the same disc. If you leave them _ in the root directory as is...they will be accessible from anywhere in _ your computer. _ These files may be modified by the astute user. Do not rename unless you _ know what you are doing. _ These files may be invoked from anywhere in your computer. For example: _ h:\anywhere.dir> FBO$ _ Do not copy any other files into sub-directories. î ÄLOWER / UPPER CASE * Case is important! Lower case is reserved for unidentified airports and user-defined intersections. ÄUSE CAPS All Navaids and Intersections are encoded in Caps. However a user may self define an intersection in lower case. Whenever that intersection is inserted in a plan its case should match. The same holds true if you elect to use a City name. To make selections from the Main Menu strike the funtion keys [F1]....[F10] It is sometimes necessary to strike [Enter] twice. [Enter] = [Return]. A [Blank] entry usually results in a return to the parent menu. This system is time sensitive.....please set date properly....Each use!!!! To cancel a flight plan operation in progress......strike [F10]. Your name etc will be burned-in after the first successful flight plan. ÄRELIEF Your intuition may tell you differently but there are three keys which usually will come to your rescue. When in doubt thump on [Esc] / [Enter] / [End]. After a predetermined period the DATA-BASES will AUTOMATICALLY be flagged as STALE DATA. î ÄOVERVIEW The following procedure is generally recommended: If you have the Weight & Balance program(s): 1) From the Main Menu enter your Name C# & Tail Number. 2) Proceed to W&B [F2]. 3) Select a "TYPE"...etc. 4) Execute an "error free" W&B. As this is an exercise the numbers entered . are meaningless. Thereafter that TYPE is linked to that Tail Number. . The exercise must be "error free"; i.e. YOU MUST DEMONSTRATE TO THE SYSTEM . THAT YOU HAVE ADEQUATE KNOWLEDGE OF THAT A/C! 5) Thereafter whenever you enter the system using that Tail Number...the . system will use the TYPE files which were involved in the exercise. 6) Do the above for each A/C which you intend to fly. If you do not have the Weight & Balance program(s): 1) From the Main Menu enter your Name C# & Tail Number. 2) Press [F7] QLOAD and make the proper entries for each entry you intend to . fly. 3) Thereafter whenever you enter the system using that Tail Number...the . system will use the TYPE files which were involved in the exercise. See the sections discussing "Fuel Burn". Do a flight plan first......then if you wish....do a Weight & Balance to check for loads....fuel burn....legality....etc. Winds Aloft may be downloaded from: 1) Weather Vendor 2) Entered manually via the Weather Menu [F10] of the Main Menu 3) [F6] of the Flight Plan Menu. When entering winds....be complete....spaces/blanks do not register. Use 0's when you mean zero. î ÄWEIGHT & BALANCE Weight & Balance and Fuel Burn and Fuel Remaining are totally and completely integrated. RECOMMENDED PROCEDURE See published manual for discussion. Note: The system will not allow fuel loads if a "Quick Load" or W & B file does not exist that corresponds exactly to the Tail Number. ÄFUEL MANAGEMENT See published manual for discussion. ÄFUEL BURN ANALYSIS See published manual for discussion. During a flight planning operation Fuel Burn analysis is computed for each waypoint enroute...and yields the fuel remaining. The algorithm for this analysis is very thorough and accurate. Fuel burn analysis will not be computed if a previous Weight & Balance or Quick Load was not performed....or if Tail numbers do not match. The hard copy output will show the fuel load. If they are zero....or if TAS=0 no fuel burn was performed. Also it is not possible to modify fuel load if no W&B nor Quick Load was performed. ÄFUEL BURNED Fuel burn rates will be adjusted for temperature at altitude. Your entries should always be for a std day. See published manual for discussion. ÄQUICK LOAD If you do not have the Weight & Balance program you may still load your aircraft with fuel....and get a reasonable fuel burn analysis. See published manual for discussion. ÄFUEL BURN SUMMARY . QUICK LOAD | W & B | TAIL NUMBER | Comment . -+-----------+-------+-------------+------------------------------ . | N | N | - | No fuel burn . | Y | N | No match | " . | N | Y | No match | " . | Y | N | Match | Fuel Burn as per QLOAD . | N | Y | Match | " " " " W&B . | Y | Y | Match | " " " " W&B . -+-----------+-------+-------------+------------------------------ Notes: W&B takes precedence. . Quick Load may be used to "touch-up" modify a W&B solution. . Selection of A/C "TYPE" can only be done via W&B. ÄTAIL NUMBER See published manual for discussion. Tail Number is controlled/dictated by the entry made from the Main Menu. Fuel burn analysis will not occur unless the Tail number of the current aircraft = Tail number of the aircraft loaded via "Quick Load" or W & B. ÄFUEL BURN / TAIL NUMBER PROCEDURE See published manual for discussion. ÄMULTIPLE A/C SAME TYPE See published manual for discussion. î ÄMODEL See published manual for discussion. MODEL is contained on the WEIGHT & BALANCE floppy disc; i.e. C:\> MODEL. If you need and fly an aircraft which is not in the data-base you may create your own file by using the MODEL procedures.......and the aircraft manuals. î ÄFUNCTION KEYS _tbd = to be determined. The following apply during: menu>---------{main}-----------|-------{airports}-----|--------{w&b}--------- [F1] SEARCH = search query | STATES = state menu. | TYPE = seclect type. [F2] W&B = w & b | tbd | RSTRT = restart. [F3] CLRNC = flight plan. | tbd | MODFY = modify load. [F4] CHART = graph last | tbd | tbd [F5] LOCATE = show intrsctn.| tbd | tbd [F6] AIRPRT = afd's. | GRAPH = diagram. | tbd [F7] QLOAD = Quick Load | tbd | tbd [F8] AUDIT = audit menu. | PRINT = prnt screen.| MODEL = create a/c. [F9] WEATHR = enrte weather.| tbd | CLRNC = flight plan. [F10] WINDS = winds aloft. | MAIN = main menu. | ABORT = main menu. [End] | | Process............ [Esc] DOS................... | Previous Menu...... | Abort.............. The following apply during Flight Planning operations (FLIGHT PLAN MENU): _ St: = Start/From De: = Destination/To [F1] tbd [F2] tbd [F3] tbd [F4] tbd [F5] Enable manual WINDS entries. Automatic in the `wind' state. [F6] Reverse the Plan. In the [FLOPPED] state will not save. [F7] Altitude optimization with [F5] = `winds` [F8] Toggle Topographical/TCA-MOA-RESTRICTED simulation on/off. [F9] Toggle Rhombic/Great Circle solution for Option -K-. [F10] Cancel an operation in progress. [End] Depress & hold for quick winds sequence/process/compose plan. [Esc] Previous Menu. [***] Strike [End] or [Enter x 2]....when in doubt. Chartmaster graphic functions are displayed on graphic help screen. ÄCONVENTIONS ÄSYMBOLS . `*' City / Terminal area (Low Enroute) *WASHINGTON . `**' " " " (Jet " ) **WASHINGTON . `*!' " " " (Tower-Tower) *!WESTCHESTER . `*^' " " " (13000-17000) *^HAMILTON . `**^' " " " (23000-45000) **^BALTIMORE . `*#' " " " (non-ATC) *#PORTLAND ME . `**NAnnn' Common track NAR Routes **NA123 . `**NA-nnn' Non-Common track NAR Routes **NA-TAFFY . `%' Airport %DCA (Option -K-) . `V' Victor airway Vnnnd . `J' Jet airway Jnnnd . `?' Temporarily remove from string ?bcde (Option -K-) . `#" Intersecting radial absent. ÄRESERVED WORDS _Reserved words may appear only in Option -K- plans and should not be defined by the user. _STAR used for the final segment of an ATC Preferred Rte. It should be defined as the initial fix of the TERMINAL AREA APPROACH. Enter the first fix of the procedure. _SID used for the start of a plan. Enter the first fix of the procedure. _*ORIG & *DEST are reserved for the results of Automatic routes and to recall these as non-descript routes. Otherwise change these to *Cities or %Airports. _RNAV used to solve for and insert way-points into a flight plan string. Also if direct leg exceeds 999nm....this word will fill in gap with fixes. If the system can't find 2 or more VORTAC's for fixes....a sugestion will be made to remove RNAV from the plan string. î ÄOUTPUT FORMAT _The print-out is blocked off according to the following format: _ HEADER _ ROUTE _ COMMENTS _ PLAN _ HIGH MEA/MOCA.......etc. _ SYMBOL LEGEND _ NAVAID SUMMARY _ AIRPORT SUMMARY _ DME FIX SUMMARY The Comments block: _ Comments / Function Key settings / Initial winds / KTAS / etc. The Plan block: _ Heading/GS as affect by winds at altitude (blank if KTAS = 0). _ Way-points: _ VOR / INTERSECTION / AIRPORT _ Unnamed Intersections: <-dme-> = DME fix / <-way-> = Lat-lon fix _ Airway change -----{---Vnnnd---}------ _ End of Airway & start of Direct -----{ >-< }---- _ Frequency change ( . ) _ Course from way-point (Magnetic or True) _ Xsctn: _ Intersecting radial and Vor. _ # = Intersection is fixed by DME or if Plan is pure direct _ also indicates Option -K- line #. _ TWEB / HIWAS = + _ Segment length in nautical miles. _ Distance...to next VOR...from last VOR. _ Trip Distances....From and Remaining. _ ETA at each way-point. _ Cruise altitude. _ Vertical Rate necessary to make required altitude at next way-point. . Where VR = 9999 then VR exceeds 32000 ft/min. _ Average Groundspeed corrected for winds and climb & descent. _ Cross radial dme mileage for dme-fix...also `slant range' when airspeed _ and cruise altitude greater than 0. _ MEA/MOCA*/MCA+/MAA^/MRA#/Comments/Lat-Lon low alt alert (Topo-TCA{x Alert) Symbol Legend: _ +=TWEB/HIWAS #=DME Xsctn SEG= nm to next waypoint. _ MEA/MOCA...= msl x 100' to next waypoint. _ VR = Min Vert Rte req x 10 fpm _ avg = Average GSPD last leg with climb/descent with windage. _ `x' = Required flight path angle exceeds 9.35 deg or 1000 ft/nm _ `y' = MEA alert. _ `xxxx' = Vertical rate not computed for this waypoint. Usse next wp. DME fixes are corrected for altitude exactly when TAS and Cruise Altitude > 0. _THE HIGHEST MEA IS COMPUTED IRREGARDLESS OF DIRECTION. LOWER ALTITUDES MAY _BE POSSIBLE FOR THE DIRECTION OF FLIGHT. _ALL USA & CANDIAN ROUTES AND ALL OMNIS ARE CONTAINED IN THE DATA-BASE. The Navaid Summary: * Navaid ID's / frequencies / TWEB / Lat-Lon / City & State / Winds Aloft _ for that way-point. If the winds aloft file is empty then 0/0/0 will appear. _ If a wind direction is given with no speed...then winds are calm. * Also shown in the Navaid Summary: < = Low service (within 7 nm of Airport) * = Terminal service (at field) _ Elevation for the overflown Omnis. * Zero elevation means S.L. or unknown. * Ideal for Loran users. Key in the Lat-lons where "elevation" is indicated. The Airport Summary: * The Airport ID / City & State / Elevation The DME fix Summary: * The Fix Name / Radial / VOR / DME / Frequency / Channel * Lists all fixes defined by DME & Radial only. * Ideal for pure RNAV users. ÄERRORS _Errors are reported on line 1 of the screen. `#' Errors are DOS type. î ÄDOS COMMAND LINE INTEGRATOR INSTRUCTIONS It is possible to process print graph & chart a plan without going through a single menu.......... ---------------------------------------------------------------------- . - CLEARANCE DIRECT ACCESS DOS MENU INSTRUCTIONS - ---------------------------------------------------------------------- . FBOZ {function} {function}-----------------------------{function}--------------------- .graph = (G)raph last plan. <│ listplan = List last plan. .navsum = Nav Summary last plan. │ print = Print last plan. < .auto = Automatic routing. <│ rnav = RNAV planning. < .plan = Compose mixed plan. │ airport = (AFD) & Diagrams.< .w&b = Weight & Balance. │ model = Build A/C Models. .main = MAIN menu/Weather/DUAT. │ menu = Flight plan menu. .manual = Print manual. │ help = Help screen. .search = (S)earch by City name. │ recall = Recall last plan.< .navaid = Look-up (N)avaid. │intersection = Look-up (I)nterxs. .reset = Reset initial parameters │ autoexec = Reset computer. .alarm = Set alarm & vendor. <│ fuel = Quick load fuel. .extend = E(x)tended functions. <│ pref = Preferred menu. < --------------------------------{shortcuts}---------------------------- .FBOZ (?) = {function} │ FBO$ = Main menu .FBO! = Flight Planner │ FBOHELP = Help ----------------------------------------------------------------------- . Current drive is default. - Letters in () may be substituted for the whole word. _ e.g. FBOZ G = FBOZ GRAPH ------------------------------------------------------------------------ . - CLEARANCE EXTENDED ACCESS DOS MENU INSTRUCTIONS - ------------------------------------------------------------------------ . FBOZ {function} [C/D/E/F...] {1} {2} {3}......{9} .{function}------------------------------------------------------------- . airport {ID} {STATE} = Display airport AFD. . airport {ID} {STATE} P = Prn airport AFD. . airport {ID} {STATE} P D = Prn AFD & runway diagram. . airport {ID} {STATE} X D = Prn rwy diagram. . airport {ID} {STATE} X I = Prn rwy diagram reduced radius. . graph {R} {Nav/%Apt} = Grf route w/map centered on {}. . {#} {R} {ID} {STATE} P D = Print Plan-Grf route-Prn AFD. . {#} {R} = Print Plan-Grf route. . {@} {Start} {Destn} = Flight Plan-Grf route-Prn AFDs. . auto {St}{De}{D/V/J}{favor}{V/J}{V/J}; where {V/J} means avoid. . = Auto Plan-Grf route-Prn AFDs. . alarm {weather vendor #} {lcl time} {pref/auto/rnav/print}... . = Fetch Winds-extended function. ------------------------------------------------------------------------ . Where X=Skip process . - e.g. FBOZ AIRPORT LAX CA P G / FBOZ AUTO LAX %BOS V 3 V16 V123 . Where {#} = print / recall . - e.g. FBOZ PRINT R STL MO P G / FBOZ RECALL R / FBOZ PRINT X STL MO . Where {@} = rnav / pref....(use `_' w/city names). . - e.g. FBOZ RNAV LAX LAS / FBOZ PREF **BOSTON **WEST_PALM_BEACH . - e.g. FBOZ ALARM 2 11:40 PREF *BALTIMORE *O'HARE / FBOZ ALARM 2 07 RECALL R î Ä-------CLEARANCE FLIGHT PLANNER------- Option -K- is used for advanced types of plans. Graph your plan....and you will gain a full understanding of what you have accomplished. * Plans composed with Option -K- are recalled via Option -J-. * Option -K- allows mixing with unlimited flexibility. * Generally the longer the plan the longer it takes to put together. It takes about 2 minutes on a PC/XT. Intersection & windage operations are longest. * Navaid Magnetic Variation & Elevation will be displayed in the Navaid Summary....only for those which are to be overflown....making it easy to spot. * Use `V / J' for Canadian & Mexican Routes....as if US routes. * Start & Destination may be an OMNI a RADIO or an INTERSECTION. * There are an infinite number of ways to go from place to place. This system allows the user to select his route......and to mix Victor & Jet Airways. * If allowed the system will select its own cross-over points from one route to another. However some routes cross more than once and the system may select untenable cross-overs; or you may wish to fly a more selective route by including an Omni or Xsctn. Complete editing keys are available to allow the Pilot to customize the Plan. ÄPARTITION See published manual for discussion. * 'TOO LONG / PARTITION' usually may be corrected by supplying as many airway connections as there is room for. Use the [Ins] key for this purpose. For example LAX-V16-BOS....may be partitioned into LAX-V16-TUS-V16-BOS. Also turning off "Low Altitude Alert" [F8] will help. If that doesn't work....the plan is too big and must be broken up into two or more segments. î ÄFlight Plan Restrictions 1)Automatic Airway Linking may occur only at published Navaids & Intersections. 2)Automatic Routing will route only through Navaids. The solution may route _ through an intersection. 3)For Plans which solve for magnetic course(s) consecutive Lat-lon; or _ %Airport lat-lon sequences are not allowed. There are no restrictions for _ True course(s). 4)RNAV must be preceeded and followed by any: _ a) Navaid b) Intersection c) DME fix d) %Airport 5)Blank 6)An Airway may be preceeded or followed by another Airway which links at a _ published Navaid or Intersection only. 7)An Airway may be preceeded or followed by a published Navaid or Intersection _ which resides on that Airway. Comments: See published manual for discussion. î ÄFlight Plan Menu Option -G- See published manual for discussion. ÄKTAS Step 1 in any Fight Planner operation is to select Option -G- and set your KTAS and Initial Fix altitude. (With KTAS=0 no windage is computed...and the process is therefore quicker). KTAS should be set to STD DAY AT SEA LEVEL for the power setting (%BHP) that you intend to fly...from your manual. Corrections will be made for temp at alt climb & descent...depending on the prevailing weather at time of plan. ÄMaximum altitude See published manual for discussion. No optimization will occur above your maximum + 1000ft. î ÄAUTOMATIC AIRWAY LINKING * Airways may only link at Navaids or published Intersections. Where such a link does not exist a 'No Link' message will be flashed. For example under Option -K-....way-points: . HNK__ |....... . J68__ |....... . V130_ |....... . ORW__ |....... J68 & V130 cross each other....but not at a Navaid or published Intersection. To keep track of all criss-crosses would require a data-base way beyond the capacity of a PC....and since few flight plans require this type of airway switch we decided it was not worth the space...especially since we have a way to solve for this point. Visit the Main Menu [F5] and type [zzzzz]......Enter the following (zzzzz is a throw away dummy self defined intersection not saved): . deg frm deg frm dme . 093|HNK|329|ORW|000| The system will yield: . deg frm deg frm dme . 093|HNK|329|ORW| 32| or 32 DME on the 329 degree radial from ORW. The plan should the read: . HNK__ | ______ | _______ | _________ . _____ | ______ | _______ | 032329ORW . ORW__ | ______ | _______ | _________ The results in either case are identical. (Lat-lon if you know it is ok). Note: If the resolution is zero (0) or the Navaid itself...nothing is done. This is the only instance where the user may have to refer to a chart. However since the plan is saved this exercise need not be repeated. See ATC routes for examples. User defined intersections may take the form `nnnnn' to comply with NOAA. Such an intersection may have the name.....`12345'. Usually this is the tag given to a lat-lon intersection of two airways....or a Turning Point. Suit yourself...this planner will handle it. The exact position of the intersection of two airways may be impossible to solve for. Only a database of these intersections will work....but it is not feasible to maintain such a database in a PC. There isn't enough room....and the need for same is rare. (If they cross more than once...which one is the correct one?....etc) * If allowed the system will select its own cross-over points from one route to another. * Some Airways are in bits and pieces scattered throughout the USA...and some of these criss-cross each other several times. The program does its best to make some sense out of this scheme but sometimes the job is overwhelming and a `No link' message may be flashed...where some link does exist. Try flipping the airway sequence...or include feasible connections. * If the routes cross only once.......cross-overs do not have to be specified ....linking is completely automatic & sufficient. î ÄCITY-to-CITY See published manual for discussion. î ÄMIXED PLANS ÄFlight Plan Menu Option -K- ÄWAY-POINT SCRATCH-PAD _This scratch-pad is block off into three (3) fields: _WAYS (14 alpha-numeric) / LAT-LON (13 numbers) /DME FIX (9 alpha-numeric) _WAYS = City (14) / Airway (5) / Airport (5) / Intersection (5) / VOR (3) _LAT-LON = Latitude / Longitude _DME FIX = Dme distance (.01-999) / Radial from (OOO-360) / VOR ÄEnter only one type of WAY per line. _Each line contains one type descriptor only: either or....not both or more. . e.g. %ABC is sufficient to describe an airport etc. _Write City names thru & into N.Lat field preceeded by an `*' _Enter Way-points in the proper columns (Fields). _Some presentations are redundant to allow for future development. _Include zero's for fields which are numeric. To create your own Terminal-to-Terminal Way-point Plans * From the CLEARANCE MENU select Option -K-: _ Name of originating Terminal...... 1.-*LOS ANGELES____|_______| _________ _ START (airport)................... 2.-%LAX ______|_______| _________ _ Direct segment (intersection)..... 3.-SAUGS ______|_______| _________ _ Victor Airway..................... 4.-V165 ______|_______| _________ _ Crossover......................... 5.-EHF ______|_______| _________ _ Connecting Airway................. 6.-V23 ______|_______| _________ _ Final fix on Airway............... 7.-CZQ ______|_______| _________ _ Lat-Lon position fix.............. 8.-_____ 361234|1191234| _________ _ DME fix........................... 9.-_____ ______|_______| 045011CZQ _ Reserved word.....................10.-FRA__ STAR__|_______| _________ _ END (airport)...................10.-%FAT ______|_______| _________ _ Name of destination Terminal......11.-*FRESNO ______|_______| _________ _ Press [End] * To recall the plan....from the CLEARANCE MENU select Option -J-: _ Name of originating Terminal......*LOS ANGELES _ Name of destination Terminal......*FRESNO _ Press [End] * The first blank line or the second *CITY terminates input. City names should appear only as the first and / or last entry. * To tempoarily remove an element from Way-point plans insert "?" as follows: ...?165 (removes V165 from the plan. SAUGS-EHF becomes direct). A Plan which contains a "?".....WILL NOT be saved. * If an Airway segment is included.........Airports and Lat-Lon fixes must not follow each other in any combination of sequences. This restriction does not apply if an Airway segment is not included or the course is TRUE. * If an Airway segment is included.......the Fixes before and after the Airway sequence must lie on the Airway. However no Fix is required between Airways. Linking of Airways is automatic. * Strike [Esc] to return to FLIGHT PLAN MENU...then Option -K- to re-iterate. * Multiple routes for the same Cities can be entered e.g. *LA#1 / *LA#2..... * Inorder to differentiate both Victor & Jet Preferred Routes for Option -K- for the same Cities use `**' for Jet Routes e.g.: _ *PORTLAND...............for an ATC Victor Route _ **PORTLAND..............for an ATC Jet Route _ This convention has been adopted by DATA-PLANE but is strictly arbitrary to accomodate the above differentiation. Option -K- is flexible in this respect. Inorder to protect a Route from being overwritten by the ATC Preferred discs the user may wish to adopt another convention e.g.: _ *#PORTLAND........etc. thus enabling several CITY-to-CITY Option -K- Routes to exist at the same time. Another convention that is popular is lower case letters e.g.: _ *Portland........etc. _ _ "PORTLAND" does not equal "Portland". * Any Stored Route may be modified by simply re-doing. ÄMIXING ROUTE TYPES See published manual for discussion. * Option -K- allows unlimited mixing of route types. * To create a plan which solves for way-points in a Direct segment insert the reserved word `RNAV' between any two way-points. This is an Airline application. î ÄPREFERRED See published manual for discussion. ÄATC PREFERRED CITY-to-CITY ÄFlight Plan Menu Option -J- See published manual for discussion. ÄFlight Plan Menu Option -P- * After graphing...or any operation...the last plan saved may be pulled down. ÄEXTENDING ATC PREFERRED ROUTINGS See published manual for discussion. ÄPARTIAL ROUTES * After composing a flight plan you may wish to create a plan which is only a part of the total plan. Because Option -K- terminates on the first empty line (or second *City) simply move the cursor to the line following the way-point you wish to make the final fix.........and strike [Ins]...then [End]. The plan will be composed up to the blank line just created....without erasing the original long plan. ÄNORTH AMERICAN COMMON/NON-COMMON ROUTES See published manual for discussion. î ÄWINDAGE The system will compute windage anytime KTAS > 0. It will perform windage calculations with or without a download winds aloft file...and is very flexible in this respect. If the system finds a winds aloft file it will use the contents of the file to compute windage. If it finds the winds aloft file empty it will compute windage based on manual inputs & the state of various toggles. In short if winds aloft have been downloaded or entered manually off-line via [F6].....KTAS > 0....and [F5] is in the `winds` state...windage is accurate and current. ..[F5]..|..winds aloft..|..dir/spd/temp..|..altitude..|..windage..... `winds` | downloaded | current | profiled | accurate `winds` | empty | enter off-line| profiled | yes `winds` | empty | empty | profiled | no `WINDS` | downloaded | current | user | accurate `WINDS` | empty | enter on-line | user | yes `WINDS` | empty | empty | user | no Altitude `profiled` = above MEA's...& terrain clearance with [F8] = `Alert` or best winds above MEA's with [F7] = `optimiz` ÄWINDS ALOFT ÄFlight Plan Menu [F5] Toggled with [F5]. In the disabled state `winds` will compute windage but will not stop for winds up-dates & will automatically create flight profile complete with cruise altitudes. Convienent for repetitive plans. If the flight plan begins at a location which does not report...then Initial winds should be set in the 'WINDS' state.....enter the winds at the field... then toggle [f5] to the 'winds' state.....for automatic winds aloft fetching thereafter. The reason for this is that the weather at some locations cannot be determined with any accuracy.....we have have therefore left them for the user to enter. The following sequence is recommended: . From the Main Menu...........[F10] Download winds via modem. . From the Flight Plan Menu....Run a flight plan Option w/KTAS > 1kts . and [F5] in the `winds` state. . Escape to the Main Menu . Select Weather [F9] ÄTEMPERATURE Temperature corrections at altitude will be made following the first non-blank temperature field. This method allows the user who has not downloaded winds to run a flight plan against winds only...as when only the initial winds are set. Otherwise the user would be required to enter temperature for every way-point when his purpose may be to run the plan for effect only. Otherwise the planner would interpret blank fields as 0 degrees Celsius.....or carry spurrious temps to altitude. Therefore blanking the temperature field of the `initial wind` set will allow a reasonable plan to be composed with winds. This concept is very interesting and very instructive for those who wish to see the effect of temperature on performance. Of course downloaded winds aloft will be composed with all variables and temp. ÄOPTIMIZATION OF ALTITUDE ÄFlight Plan Menu [F7] The optimization algorithm is based on a cruise constant power (%BHP) concept. Select a KTAS based upon a %BHP which you know that you can maintain at altitude. Most aircraft can maintain between 65 - 75% BHP to their service ceiling. You may be assigned an altitude at which you cannot maintain 80%. Errors induced by this condition are usually negligible (2%). However it bears watching if you intend to fly at the edge of your fuel capacity. With this switch set to the `optimz` state the system will attempt to climb or descend in accordance with the best prevailing winds.....according to the following rules: 1) [F5] must be in the `winds` state. 2) Cruise altitude must be greater than 4000 ft and less than your Maximum . altitude. 3) A winds aloft download must be current. WILL NOT OPTIMIZE at locations . where it finds empty winds aloft items...as just after "Wind Scrub". . Further it WILL NOT OPTIMIZE at locations where either Dir/kts/Deg C are . blank. (A zero is a non-blank). Tis better not to guess. Especially . where specific fuel consumption is concerned. Therefore....when manually . entering winds....give all three parameters if you want them to register . for optimization. 4) Altitude will be changed where there is at least a 5 kts gain in GS. 5) There must be at least 100nm remaining in the trip for the altitude to . be optimized upwards. If the resulting plan is too much like a roller coaster...set [F7] to the `NOPTMZ` state....and with [F5] in the `wind` state....the resulting profile will climb above the MEA's and stay there. In some cases optimizing results in slower ground speed due to the loss incurred during frequent climbs. This may occur when the plan attempts to descend to lower altitudes...only to find that downstream the MEA's require a climb back to higher altitudes. You may also toggle [F7] in real-time.....and thereby get a portion of the plan optimized. You may notice in actual flight that your KIAS is higher or lower than the KTAS which you entered for the plan. This is normal as it is rare that Std day conditions are encountered and the plan has adjusted ground speed for expected temperature at altitude. ÄENTER WINDS MANUALLY OFF-LINE ÄFlight Plan Menu Option -F- See published manual for discussion. When manually entering winds....give all three parameters if you want them to register. Do not leave a field blank. (Zero is non-blank). This option provides a quick reference when you only have the Navaid ID. Location and other information is convienently displayed. Do not confuse this with the Manual entry option availble with the 'Winds Aloft Weather Menu'.....which is the comprehensive method of manual winds entry. These winds will not be geographically disbursed. ÄENTER WINDS MANUALLY ON-LINE See published manual for discussion. * Winds aloft are available for altitudes up to 53000 ft. If the Winds Aloft file has not been refreshed/scrubbed...random special characters will appear. * ONLY....IF KTAS > 0....Will Winds Aloft procedures will be active. Ä`winds` state. No choices. All windage is computed automatically. Ä`WINDS` state. * This state allows you to override the winds aloft file...or to enter winds manually on-line if you have not downloaded the winds aloft via modem. In this state the climb / descent will not automatically change. You control everything in this state. * As each way-point is encountered the Plan will stop and request Winds. What you enter will affect the heading at that point. As each Intersection is encountered winds for the nearest Navaid will be requested. In the event the Navaid is too far and does not apply enter the winds for the Intersection irregardless of the Navaid being suggested. Usually the Navaid is appropriate. (`#' refers to an internal ID of an intersection or way-point for Option -K-). * Enter WIND DIR (true)/KTS/TEMP/...change Altitude if desired. The Winds Aloft file WILL NOT BE UP-DATED....BUT WHAT YOU ENTER WILL AFFECT THE PLAN. * Any unchanged field will be passed to the next way-pont. If you desire no changes after a given point....simply press and hold the [End] key. * If any field is blank...the last reported DIR/KTS/TEMP/ALT will be assumed for that segment of the Plan. * Winds for the destination terminal are redundant. * The WINDS ALOFT file is purged & refreshed every 6 hours. * Enter Wind direction TRUE....temperature as degrees CELSIUS. * The Heading & Wind direction on the printed output will correspond to the type of flight plan developed. For example if the Course is TRUE the Heading & Wind direction will be TRUE; as is the case for Direct plans. If the Course is Magnetic the Heading & Wind direction will be Magnetic; as is the case for a Victor flight plan. This will facilitate establishing crab angles in flight. ÄCONSTANT WINDS * If the winds are constant throughout the route...enter winds at the `initial winds insert`....and press and hold the [End] key....or set [F5] to the `wind' state....then strike [End]. ÄINITIAL WINDS See published manual for discussion. î ÄCLIMB / DESENT The system will attempt to establish a profile based on the following rules: _1)Airports set the altitude if they are the start or end. _2)The first fix will set the altitude if it is off an airway. If it is on an airway....altitude will be set to 3000'+ for a Victor airway; and 19000'+ for a Jet airway. Airway altitudes will override the first fix altitude request. For example if your first fix is on a Victor airway and you are traveling west.....the altitude will be set to 4000'....unless there is an altitude restriction at that point...in which case the atltitude will be set higher to comply with the restriction. _3)With [F5] set in the `winds' state....the profile is set automatically. _4)With [F5] set in the `WINDS' state....the user sets all altitudes. _5)A topographical obstacle will drive the altitude upwards +1000'. _6)Airway ceilings will not be penetrated. ÄCRUISE ALTITUDE If the Cruise Altitude is less than any MEA the MEA will become the Cruise Altitude for the trip from that point onward....if in the automatic [F5] mode; and a message will be flashed (CRUISE<MEA)...and a `y' will be inserted into the Cruise column of the hard copy.....as a warning of possible MEA conflict (Low Altitude Alert) for the previous leg. The Highest Cruise Altitude will be passed to W & B thru the XTALK file. When the system detects an %Airport as the start or end it automatically lowers the altitude to the airport elevation. ÄCHANGING CRUISE ALTITUDE * You may change the cruise altitude in real time by toggling [F5]. At any point toggle [F5] to the `WINDS` state and the plan will stop. Enter the altitude you desire. To return to the real-time mode...set [F5] to the 'wind' state....strike [End]. ÄINITIAL FIX ALTITUDE * This is a very tenuous place at best. You should know about where you expect to be and about how far the initial fix is...beyond that the flight planner takes over...and has a tendency to go up. [F5] of the Flight Plan Menu gives you further control over this section of the profile. Also ATC may not clear you exactly as planned...so be ready. If it becomes untenable to establish this fix...simply insert your desired cruise altitude. This is a very helpful tool if your first fix is off an airway. Also if you set this value to cruise...the planner will ignore an MEA profile and get you up there in a hurry. * This parameter allows you to select a first fix and altitude you expect to achieve at that fix. Otherwise the plan might optimize to an altitude which cannot be achieved by your aircraft. Low altitude alert will not be computed for the first fix. Otherwise airports in the vicinity of a high mountain may plan out as untenable climb profiles. It is assumed that you know the area. Think of it as the starting altitude after which all kinds of things start happening. In short you can place yourself at a known point in space exactly before winds take effect. * Enter the altitude you wish to achieve at the first fix. This height will continue to appear with the first fix and is convienent for repetitive plans which depart to the same fix. It is remembered from session to session. If the initial fix altitude is greater than the MEA at any point it will effectively become the cruise altitude...when [F5] is in the `winds`state. Most users set initial fix altitude to cruise....as the system makes adjustments for climb in the given weather conditions anyway...and errors have been negligible. In practice the process makes more sense...and is automatic. * If you elect to fly to an initial fix keep it within the vicinity of the airport. In other words don't set your initial fix altitude to 1500ft and attempt to fly to a fix which is 60 miles away. Define a fix from the Main Menu [F5] which is reasonably close to the airport. * The above procedure along with other variations and Options spoken of elsewhere allow the pilot user to repetively fly the same route at different altitudes....against the same weather system.....and judge the differences. ÄENROUTE with Laptop. See published manual for discussion. * If you are enroute and have a laptop in the cockpit....simple reset the 'initial fix altitude' to your current altitude....when you want to get a plan composed enroute...as when you receive an amended clearance. î ÄMAGNETIC COURSE See published manual for discussion. ÄTRUE COURSE See published manual for discussion. Please note that Chartmaker graphics will convert all TRUE course to magnetic. ÄLOW ALTITUDE ALERT (TOPO) ÄFlight Plan Menu [F8] See published manual for discussion. * This feature is in addition to the MEA Alert.......and is engaged only when Function key [F8] of the CLEARANCE FLIGHT PLANNER is in the [ALERT] state. ÄTCA / MOA / RESTRICTED AIRSPACE ALERT ÄFlight Plan Menu [F8] See published manual for discussion. * This feature follows the same rules as the Topographical relief data-base. ÄVERTICAL RATE * Whenever the system detects a change of altitude....a minimum vertical rate feet/min is computed.....along with an approximation of the flight path angle required to make the next altitude over the distance of that leg taking into account the wind conditions at that waypoint. * If the Angle exceeds 9.35 degrees....or 1000 ft per nm...an `x' is inserted into the Average Groundspeed column of the hard copy. This constant is convie- nt as it lends itself to easy mental calculation; e.g. @ 120 kts groundspeed you need at least 2000 fpm vertical rate....for every mile. It is the pilot's responsibility to determine if the flight path angle is obtainable for his flight. ÄAIRSPEED See published manual for discussion. * If KTAS=0 then no windage will be computed. KTAS is remembered from the last session until changed. It is convienent to enter your own aircraft KTAS. ÄHDG/GS * Heading & Ground Speed are a function of windage....and indicate the speeds expected at the fix. ÄAVG/GS See published manual for discussion. * The average groundspeed expected over the previous leg. ÄLET-DOWN POINT See published manual for discussion. * Due to the possiblity of terrain conflict surrounding the target airport the let-down point is not computed. It is the pilot's responsibility to familiarize himself with the destination airport and its unique approach procedures. However an abundance of flight data is provided to assist the user in planning his approach. ÄFLIP-FLOP ÄFlight Plan Menu [F6] Plans composed with Option -K- may be flipped. With [F6] in the `FLOP` state plans will not be saved. î ÄRNAV There are three (3) ways to solve for RNAV. ÄRNAV (pure 22 way-points) ÄFlight Plan Menu option -M- * Must Start & End at a Navaid Xsctn Dme Fix or %Airport. * Lat-Lon's and undefined Xsctns etc. are not permitted. * This type plan draws a GREAT CIRCLE line from the Start to the Destination then selects VOR'S in-between which would make tenable DME fixes. This is automatic. * VOR'S are selected which are no more than 75 nm off-course and which offer a DME Channel. All others are rejected. Waypoints are selected by the Great Circle solution but point to point steering is Rhombic. * Rhombic magnetic course and distance are indicated. This is the most practi- cal method for hands-on-flying. More sophisticated avionics for Great Circle navigation are accomodated by LAT-LON and DME fixes available with hard copy. ( [F9] not available with this selection). * Even though the course appears to change due to magnetic variation enroute the course flown is mostly straight-line. Before assuming that the course has changed....check the Magnetic Variation. However because this system attempts to locate Way-points based on integers so that exact DME readings can be obtained some minor course variations will occur due to rounding. The course is then re-computed to account for this rounding; and therefore the way-point lat-lon is exact. These variations may be as much as 3/4 mile off course from a perfect straight line. * Because of this effect some stair-casing and swinging may occur where the legs are shortest.........this effect has been noticed to occur mostly on routes which are due East-West. If the route produced is not desirable switch to Direct and select your own Way-points. * Only VOR's with DME channels are selected for waypoint fixes. If the route gaps....or if the waypoints are too far apart.....break the Route up into two or more parts....and instead of 16 waypoints obtain 32 waypoints.........etc. * Occassionally a way-point will be selected which is less than 1 nm from the target. This way-point is superfluous and should be ignored. * Do not fly the course....fly to the fix. The course is a guide to the fix. On many RNAV segments due to distance etc. your only reference to the course is your compass....which fluxuates with magnetic declination(s). * It is not necessary to use all fixes. The program is designed to yield more fixes than required to fly the great circle. Chartmaker graphics will help in the selection process. Using all fixes is ok....but adds to the workload. ÄRNAV (Reserved word in route string) To include an RNAV segment in a plan which has other type segments: _ Name of originating Terminal...... 1.-*LOS ANGELES CA_|_______| _________ _ START (airport)................... 2.-%LAX ______|_______| _________ _ Direct segment (intersection)..... 3.-SAUGS ______|_______| _________ _ Victor Airway..................... 4.-V165 ______|_______| _________ _ Crossover......................... 5.-EHF ______|_______| _________ _ Reserved word..................... 6.-RNAV ______|_______| _________ _ END (Navaid).................... 7.-SEA ______|_______| _________ _ Name of destination Terminal...... 8.-*SEATTLE WA_____|_______| _________ _ Press [End] To fly an RNAV plan which includes a specific Navaid enroute: _ Name of originating Terminal...... 1.-*LOS ANGELES CA_|_______| _________ _ START (airport)................... 2.-%LAX ______|_______| _________ _ Direct segment (intersection)..... 3.-SAUGS ______|_______| _________ _ Victor Airway..................... 4.-V165 ______|_______| _________ _ Crossover......................... 5.-EHF ______|_______| _________ _ Reserved word..................... 6.-RNAV ______|_______| _________ _ Included Navaid................... 7.-RDM ______|_______| _________ _ Reserved word..................... 8.-RNAV ______|_______| _________ _ END (Navaid).................... 9.-SEA ______|_______| _________ _ Name of destination Terminal......10.-*SEATTLE WA_____|_______| _________ _ Press [End] NOTE - RNAV will not work if the `Start` or `Destination` is undefined. For example where %Airport is the `Destination` and the Airport Facilities Directory is not installed. RNAV is also an alterative with the Automatic Option -L- i.e. DIRECT. î ÄMAGNETIC VARIATION See published manual for discussion. * There is no mathematical formula for Magnetic Variation. DME fixes borrow their variation from the intersecting Navaid. ÄWAYPOINTS See published manual for discussion. * Please keep your entries inside the boundaries as indicated. * Include zeros instead of spaces where appropriate. * To establish the LAT-LON of an intersection select Option -K- and insert the name of the intersection twice. Other interesting combinations can be tried with good results. * To establish the DME fix of an Interesection given the Lat-Lon select Option -K- and insert the Navaid on line 1. & the Lat-Lon on line 2. The solution will be TRUE. adjust for mag var....or insert a dummy DME fix to cause a MAG solution as follows: _ 1.-VOR _ 2.-_____ ______|_______ | 000000VOR (dummy fix for mag var) _ 3.-_____ 123456|1234560 | _________ * Consecutive Lat-Lon fixes shud not occur in Plans which are magnetic course. Ä* Assume nothing! Check everything! î ÄINTERSECTIONS ÄMain Menu [F5] * Intersections may be modified and/or defined with [F5] of the MAIN MENU. Once entered via this method....further definition will not be required during a Way-point operation. (Airports abide by the same rules...but must be preceeded by an `%'). This type of entry is not protected during an Install. This assures re-evaluation of the fix each up-date. If you have fix which you must redefine each install...let us know and we we'll place it in the database permanently. * Any point in space may be defined with [F5]. Simply enter any five character unique name and define it. The system will remember it when it sees it in a Flight Plan: _ e.g. Z1234 * DME fix of: Rad Dme _ rrrVORddd where ddd >= .10 nm _ Use the shortest DME possible. 1/2 degree error/100 nm will miss by a mile. * By striking [F1] the format may be changed to Lat-Lon. Enter west longitudes and north latitudes. * Intersection Cross Radials are always Magnetic FROM the VOR / NDB. This varies from the Course rule...which is always from or to according to the OBS setting for that portion of the leg. ÄINTERSECTING RADIALS * From the Main Menu strike [F5]. Choose a name for this point in space which will be unique e.g. `abcde`....[Enter]. Then type in the intersecting radials: . DEG~FRM DEG~FRM DME . 096 VNY 076 LAX 000.....The DME field should be zero or blank. In the example above the solution will be the DME fix from LAX on the 076 radial: . 096 VNY 076 LAX 044 Reverse the navaids...and the result will be: . 076 LAX 096 VNY 051 Whenever the Flight Planner sees `abcde` it will know it as the DME fix from LAX on the 076 radial. Re-enter each up-date to insure currency in case the Navaid has been moved or re-surveyed. * No solution will occur if: . 1) The DME field is greater than 0. . 2) The DME exceeds 999 nm. . 3) A Navaid is unknown to the system. . 4) The radials do not intersect. . 5) The resulting DME is less than 0.1 nm ÄOFFSHORE INTERSECTIONS * A data-base of Intersections is now available for routings in the Atlantic Pacific Gulf and Caribbean areas. î ÄNAVAIDS All US & Canadian VOR's appear in the flight planning data-base. ÄNDB Not all NDB's are available as part of the flight planning data-base. They are too low powered for cross-country navigation. NDB's which have DME facilities are included. All NDB's associated with an airport appear with Runway diagrams. ÄAPPROACHES LOM/LMM NDB's normally associated with approaches are included with the intersection data-base; and appear as their five (5) letter designation. Strike [F1] change format to view the lat-lon. * This type of radio when included in a flight plan should be designated as a 5 letter intersection. It will mostly be used as an approach fix. Flight plans may be composed right to the LOM/LMM....or to some fix on the approach. ÄAPPROACHES INITIAL FIX (IAF) The intersection data-base is currently being expanded to include approach fixes recommended by ATC. The approach fix dme is given in tenths of a mile whenever the fix is closer than 10 nm...for high accuracy. RNAV approach fixes are also included. Plans may be composed directly to the IAF. î ÄAIRPORTS See published manual for discussion. * The Airport Master diskette is required. It makes all 9000+ airports _ addressable as waypoints. Each cycle the old AFD information is purged. * The AFD's are optional. They contain airport data + runway diagrams. * Airports should be entered as the 4 letter identifier.....preceeded by `%': _ e.g. %BFI or %3CUA * The fix for an airport may be entered with [F5] of the MAIN MENU. Military users will find this helpful. See Intersections for further details. * Especially for Helicopters and others who prefer to file Airport to Airport to Airport....and want Mag Vars.......the following procedure is suggested: _ Enter Airports as DME fixes e.g. %BFI or %3CUA....and define. ÄAIRPORT PICTORIALS Pictures of airports which have published approaches divided into 15 volumes as per NOAA.....plus all Airports for Canada (10 volumes). A great complement to the Runway diagrams. Up-dated semi-annually. î ÄSEARCH See published manual for discussion. 1.- Type in City name (NO *'s or %'s).... 2.- Use [Pg-Up] [Pg-Dn] for scrolling. 3.- Use [cursor] to select Routings. î ÄCANADA All Canadian navaids & airports are included in the Canadian-Alaskan AFD. ÄFAA form 7233-1 See published manual for discussion. ÄCHARTS & MAPS See published manual for discussion. î ÄGETTING STARTED * The following is a first exercise....not a procedure. Modify according to ability and experience....and software installed. It is assumed that the Tail Numbers were typed by Weight & Balance exercises or QLOADS. * See OVERVIEW / FUEL BURN / QLOAD sections in this manual. * Turn computer on. Wait for `C:\>` prompt to appear. . [Blank] = [Enter] no response. * Flight Plan Menu Options may be selected by striking a letter <A....S>: . COMPUTER PROMPT | PRESS or TYPE....then [Enter] | RESULT _____________________|_______________________________|_______________________ .1) C:\> | FBO$ | MAIN MENU . Main Menu | [F10] | Weather Menu . Weather Menu | * | Set com: port . Weather Menu | P / T | Set dial type . Weather Menu | A | Set Area Forecasts . Weather Menu | S Not required if downloading| Scrub Winds . Weather Menu | U | Set Log-on & Password . Weather Menu | 1 or 2 or .... | Download Winds Aloft . Weather Menu | w | Print Winds Aloft . Weather Menu | [Esc] | Return to Main Menu .2) Scrolling screen | [F3] | Request for ID/Tail # .3) | [/] | Flight Plan Menu . Option -B- flash | Select Option -G- | Enter KTAS...etc. .4) Option -B- flash | Select Option -L- | Request for Start .5) St: | MXE [Enter] | Request for Destination .6) De: | DCA [End] | Search & standby .7) Auto Selection | V | Restrictions .8) Include | [Blank] | " .9) Include | [Blank] | " 10) Avoid VOR | [Blank] | " 11) Avoid VOR | [Blank] | " 12) Avoid V / J | [Blank] | " 13) Avoid V / J | [Blank] | Condition 14) Favor shift N/S | [Blank] | Start Auto Solution 15) Scratch-pad | [End] | Start Plan solution 16) Cursor blinking | [Esc] | Flight Plan Menu 17) Option -B- flash | [Enter] | Flight Plan Display 18) Strike <any> | [Any Key] | Flight Plan Menu 19) Option -B- flash | Select Option -C- | Navaid Display 20) Strike <any> | [Any Key] | Flight Plan Menu 21) Option -B- flash | Select Option -D- | Print Plan 22) Option -B- flash | Select Option -E- | GRAPHICS 23) 2 BD set-up? | Y or N (Usually No) | Selection 24) Graphics Menu | Make selection (experiment) | Start graphics 25) Route graphed | [Esc] | Exit Menu 26) Exit Menu | [C] | Flight Plan menu 27) Option -B- flash | Select Option -J- | Request for Start 28) St: | MXE | Request for Destination 29) De: | DCA | Pooled plan recalled 30) Cursor Blinking | [Insert] | Blank line 1 31) Cursor Blinking | *MODENA | Waiting 32) Cursor Blinking | Move Cursor to line 9 | Waiting 33) Cursor Blinking | *WASHINGTON | Waiting 34) Cursor Blinking | [End] | *MODENA-*WASHINGTON PLAN 35) Cursor Blinking | [Esc] | Flight Plan Menu . Option -B- flash | Select Option -S- | Request for W&B . W & B | Load A/C and return to Main | Main Menu 36) Main Menu | [F9] | Weather Menu 37) Weather Menu | 1 or 2 or ... | Weather Briefing 38) Weather Menu | W | Print Weather Brief 39) Weather Menu | [Esc] | Return to Main Menu 40) Main Menu | [F9] | Weather Menu 41) Weather Menu | 9 | Duat Menu 42) Duat Menu | <F> | File...... 43) Duat Menu | <P> | Print FAA form 44) Duat Menu | <M> | Main Menu 45) Have a good trip.| | Note: Your Name etc. will not be burned-in until you type in same...create and solve a valid flight plan...and return directly to MAIN Menu without deviation to any other module. Thereafter your name will reappear and be repeated with the [/] at the Pilot Name request. î ÄRADAR MAP TEST See published manual for discussion. Purpose: 1) To demo the ability to download Weather RADAR maps and display these on the monitor. î ÄAUTO ROUTING See published manual for discussion. * Automatically constructs a Flight Plan generally adhering to the Great Circle Line. * Selectable as Option -L- of the Flight Plan Menu. Given a Start and End point this feature will attempt to find the shortest paths between the two. The algorithm threads its way until it has made contact with the target. * There are several sub-options: _ <D> = Direct / RNAV _ <V> = Victor airway paths _ <J> = Jet airway paths _ <A> = Additional Routings (for variety and alternate paths) * The following sub-options allow the user to influence the path: _ <Include> = Include two (2) optional VOR's in Plan if feasible. _ <Avoid > = Avoid / exclude two (2) optional VOR's from Plan. _ <Avoid > = Avoid / exclude two (2) optional Airways from Plan. _ <Favor > = Influence the path more northerly / southerly. * Routing precedence is Great Circle....then Included VORs. ÄFAVOR / SHIFT See published manual for discussion. * It is possible to cause the routing to shift North or South various degrees by entering +3..2..1.._..-1..-2..-3; with (+3) favoring most northerly & (-3) most southerly. This feature will shift only where feasible...does not affect solutions whereby the path is basically North/South anyway; e.g. Chicago to New Orleans. ÄADDITIONAL AUTO ROUTING See published manual for discussion. * This feature is included to demonstrate system versatility and may be an aid and of interest to some pilots. See (Processing of Additional Routes). ÄPROCESS ADDITIONAL ROUTES See published manual for discussion. * Before selecting this option do an Automatic Routing pass. ÄREPEAT LAST AUTOMATIC See published manual for discussion. * This option allows for fast re-iterations of previous automatic operations. î ÄGRAPHICS ÄCHARTMAKER See published manual for discussion. * After processing a flight plan it is possible to quickly graph and inspect the finished plan. Chartmaker will display in addition to the route the foll- owing: .1.-Navaid NDB names. .2.-Intersection names & DME FIX locators. .3.-V/J airway designators. .4.-Segment lengths. .5.-MEA / MOCA / MCA / MAA .6.-Airport ID. .7.-Borders and Scales. .8.-Lat-Lon fixes & frequency changeover points. .9.-Trip distance to any point. 10.-Eta at any point enroute. 11.-All airway connections to any point(s) on the route. 12.-All Navaids & all Airports in your system. 13.-Any Radial & Distance between two points. 14.-Winds Aloft at any altitude up to 53000 ft msl. 11.-A map of the entire North American continent Central America and as far _ north as Greenland...including all of Canada & Alaska. State & Provincial _ borders are also drawn in. The map size and lat-lon position may be _ manipulated for better perspectives.....with the routes overgraphed upon _ the map...in any perspective. 12.-Off-route Navaids and their intersecting radials are also drawn in _ providing the user with an unprecendented view of his plan. 13.-Additional off-route Navaids & Airports may be selected to be displayed _ with the route for better perspective...or if something does not screen _ use this option [Ins]. 14.-TCA's & ARSA's.....& RESTRICTED AIRSPACES. 15.-The screen with all route graphics may be printed. * The Graphic presentation may be manipulated for better viewing with the following functions (quasi-radar): 1.-Screen East/West 1/2 degree longitude. 2.-Screen North/South 1/2 degree latitude. 3.-Zoom in / Zoom out. 4.-Magnify & display FROM-TO. 5.-Center the screen on Navaid/Airport or Lat-Lon. * Data-Plane software supports Hercules CGA EGA VGA MCGA...including enhanced SVGA 30 line multisync monitors. IBM AT&T Olivetti Everex....and many more. * Select [F10] for help. All commands are on-screen. ÄUPPER-LEFT CORNER CUE * When magnification has reached a certain point where text etc. will probably start to appear a box will appear in the upper left-hand corner of the picture. This will help you gauge when to start a process. This cue changes depending on the magnification level. ÄNAVAIDS * Press <N> and all navaids in your system which can fit on the screen will be displayed. Press <any> when you've had enough. ÄWINDS ALOFT * Download Winds Aloft from a Weather vendor via modem. Compose a plan. Graph the plan. Select <W>inds. Winds aloft will be over-graphed onto the route. Calm winds or stations not reporting will show up as dots. ÄAIRPORTS * Press <A> and all airports in your system which can fit on the screen will be displayed. This is great for people who like clutter........and those who simply want to see which airports lie along their route of flight. Continued magnification will reveal their identifiers. Press <any> when you've had enough. * This process can be delimited by runway lengths. Enter the minimum length runways which you want to see. The length will be truncated to 1000' increm- ents. Therefore 9999 = 9000 ft & [9] will be displayed in the upper left hand corner. Enter a zero to see all airports. 9999 is the greatest length allowed. ÄRHOMBIC See published manual for discussion. * Press </> and enter a FROM point...and TO point. Chartmaker will draw a radial and display the distance between these two points. The screen will center on the TO point. You can practically flight plan on the screen. Intersections may be used only when they appear as part of the plan. ÄPATHS See published manual for discussion. At least one of the relevant navaids must be on screen for the following: * Select <V/J>: _ Airway paths will be drawn emmanating out from the route line. * Select <v/j>: _ Airway paths will be drawn emmanating out from the navaid. This _ process may be used to see where you can go if you left the route _ at a specific point. Paths are developed to the side of the off-course _ navaid....and perpendicular to the route if the navaid is present on _ the route. A good way to see where you can go....from anywhere in the _ ATC system. These functions can be combined with direct and RNAV routings _ with dramatic effect. Note: Doglegs are not indicated. ÄCENTER * The screen will center on the selected navaid/airport or...lat-lon. The lat-lon process is the moving map application. It is sufficient to enter only degrees...e.g. 39 123. * The system will accept an intersection to center on if it is part of the plan. * If the item is already centered the system will balk. Move the picture. ÄINSERT * Press [Ins] if you want to see a navaid or airport appear continuously. Route waypoints will be ignored if requested. They always show. ÄEXERCISE -I- Try the following exercise irregardless of route (printer on please): _ Press <key> | Enter | Result ----------------------------------------------------------------------- 1) <+> | STL | The position of the St.Louis VOR will be centered. 2) <v> | STL | Navaids having victor paths to STL will be shown. 3) <any> | - | Screen flashing. 4) <Pg Dn> | - | Continue to magnify until Cue appears in Upper Left. 5) <v> | STL | Connections will be made showing paths. 6) <Pg Dn> | - | Continue to magnify until Cue changes in Upper Left. 7) <v> | STL | Paths and Designators will appear. 8) <P> | - | When you've seen enough...print it. ----------------------------------------------------------------------- ÄEXERCISE -II- Execute an automatic routing (Option -L-) from "BUM" to "LAA"...Select Option -E- (Chartmaker) graphics. Magnify the route until the navaids appear as circles. The problem is to determine if a detour can be made to "HYS" and how far out of the way will it take you. _ Press <key> | Enter | Result ----------------------------------------------------------------------- 1) <v> | HYS | Paths will appear emmanating from HYS. ----------------------------------------------------------------------- If you want to stay on airways....you'll have to go to "TOP" from "BUM". Magnify further....and the airway designators will appear. Return to the Flight Planner....press Option -P-...and modify the plan. ÄEXERCISE -III- You're unfamiliar with an airport....and want to see what if any navaids are in the neighborhood. _ Press <key> | Enter | Result ----------------------------------------------------------------------- 1) <+> | %aaa | The Airport will appear centered on the screen. 2) <N> | - | Navaids will appear. Magnify for a better view. ----------------------------------------------------------------------- ÄEXERCISE -IV- You want to see how much ground is saved by going Great Circle. First do an Option -M- Rnav plan between LAX & BOS...then go to Chartmaker. The Great Circle line will clearly show. _ Press <key> | Enter | Result ----------------------------------------------------------------------- 1) </> | LAX | The FROM point. 2) - | BOS | The TO point. 2) - | - | The Rhombic line between LAX to BOS will appear. ----------------------------------------------------------------------- ÄRUNWAY DIAGRAMS See published manual for discussion. * Runway diagrams have an option which allows the user to select an airport in any state or province....once selected the user may view vectors to the runway(s)....and pop over to the Chartmaker Route Graphics to see where he/she is at. ÄETA's & TRIP DISTANCE * Eta's & Trip Distances overlap the same screen location(s) as the waypoint name. To display Eta's for Navaids....select [f1]...then [f9]. * To display Trip Distance for Navaids....select [f1]....then [f5]. * Eta's & Trip Distance can likewise be displayed for any & all waypoints. ÄTCA's ARSA's RESTRICTED AIRPACES See published manual for discussion. * Mapping of TCA's & ARSA's may be toggled on and off. The areas are shadded to distinguish them from other symbols. ÄMAPPING See published manual for discussion. ÄCOMPASS ROSES Compass roses will begin to appear when the longitude is less than 3 degrees. Off-course navaid compass roses appear when it is less than 2 degrees. ÄOVERVIEW The overview lets the user see where he/she is in relationship to the western hemisphere. Strike <any key> to return to previous screen. ÄPRINT SCREEN See published manual for discussion. * To print the screen strike [P]. <Any Key>...will abort the printing. ÄRESET GRAPHICS & PRINTER DPI * From the CHARTMAKER program strike [esc] to get to Menu. Strike <R> and make changes. If you have made the right selection the system won't ask you again. <+> selects the highest resolution for your graphics. This approach gives unlimited flexibilty. You may run graphics in more than one mode...with varying color schemes and printer dpi's. ÄMAGNIFICATION See published manual for discussion. ÄERRORS See published manual for discussion. * Please do not graph plans which have zero segment lengths.... ÄINTERSECTIONS * Inersections may be substituted for Navaids / Airports only if that Intersection is part of the plan. î ÄDUAT . "Interactive" is defined as user manual entries. The following functions are available with this module: . File / Cancel / Amend / Weather Brief . Print FAA form. . Print Log of Duat activites. ÄFILE Automatically files a flight plan composed by the Clearance Flight Planner via Duat. This is an automatic process. ÄCANCEL / AMEND Allows the user to cancel or amend a previously filed plan. This is an interactive process. ÄFAA FORM Prints the FAA filing form. ÄDUAT WEATHER BRIEF Automatically fetches a complete route weather briefing via Duat. This is an automatic process. ÄDUAT WINDS ALOFT Winds aloft are obtained from all DUAT vendors. Only CONTEL winds are in a suitable form for integration into the Data-Plane system. These are in the NWS format. Enter winds manually otherwise. ÄLOG Prints a log of all Duat activites. Retains information for 6 hours. ÄROUTE At this time the Clearance Flight Planner is far more precise and comprehen- sive than is required by Duat. The power generated by the Clearance Flight Planner sometimes creates some minor inconsistencies with Duat; which are easily corrected. Because the Clearance Flight Planner was in operation long before the advent of Duat.....some of the Route descriptions do not comply with the Duat format. For example the descriptor 'RNAV' is not acceptable to Duat...etc. When Duat encounters invalid descriptors it will stop and ask for a correction. Manually enter a correction. For example....enter 'DIRECT' as a correction for 'RNAV'. The Clearance system will shift back into the automatic mode as soon as the correction is accepted. The following are additional instructions for Duat in case the route elements are not accepted: Enter your Route of Flight. Do not repeat your Departure or Destination Airports. DUAT system will automatically incorporate them into your Flight Plan and your Route Briefings. You may use SIDS STARS JET and VICTOR Airways. If you use a SID it must be the first element of your Route. It must be a valid SID for your Departure Airport and you must specify your Exit or Transition Fix. If you use a STAR it must be the last element of your Route. It must be a valid STAR for your Arrival Airport and you must specify the Entrance or Transition Fix. Enter the Junction Fix between Airways if known. If you wish to use Latitude/Longitude specify both degrees and minutes (i.e. 4000N/07500W or 3930N/10122W). If you wish to use Fix-Radial-Distances enter the radial as three digits (001-360 degrees) and the distance as three digits (001-999 Nautical Miles). Example: ACY028050 for Radial 28 from Atlantic City Vortac to a distance of 50 Nm. ÄDUAT NOTES: 1) Your first Duat activity should start with an Access Code = "?". The . Duat vendor will assign you an access code for all future activity. . You must have an active license & medical. This process is interactive. . This activity may abort once the Access Code & Password are issued. 2) Enter the Access Code & Password. It will be remembered from session to . session. 3) Duat will not accept a 10 airway flight plan. 4) Departure time....and Fuel on board must be entered each session inorder . to insure accuracy and pilot awareness. Other items are saved and need . be entered once...and only once. A very convienent feature. 5) During an automatic process a Duat invalid entry may appear. Duat will . stop and request a correction. Intercede and make the correction manually. . Duat will return to the automatic mode. You have two (2) minutes to enter . the correct data. 6) Duat is very restrictive with regard to some item formats. For example . Type Aircraft cannot be a P-210....it must be C210. 7) All items may be modified or changed to comply with the users objective(s) . and/or Duat format(s). 8) Because and/or if you do not have the latest version of Weight & Balance . several items will appear as "????...." These are items which would be . contributed by the Weight & Balance module...automatically. You may enter . the data. These will not be remembered...as this would violate the rules . of contribution and integration driving the Weight & Balance module. 9) Keep the printer turned on. If you request a print operation....the system . will hang waiting for the printer to come on-line. It will wait up to 4 . minutes before timing out. 0) If an item is not recognized by DUAT....it sometimes may skip over the . entry and thereby put the system out of sycn. The system will appear to . hang. Resume the 'manual' mode....and as soon as the system detects that . it is back in sync it will resume the 'Automatic' mode. 1) DUAT requires operator intervention due to the need to enter hours:minutes . of Fuel on Board. For those who have DUAT translators..."\take-off.dir\*.LLL" is the log/file of all previous duat activity. î __________________________________ ÄADDITIONAL NOTES ÄTCA-MOA-RESTRICTED AIRSPACE * TCA-MOA-RESTRICTED AIRSPACE violations will be flagged in the comments field of the hard-copy print out as follows: _ {T = TCA / {M = MOA / {A = ARSA / {R = Restricted _ The above violations are possibles...if your route of flight overflies or is within 4nm of the Airspace border. See published manual for discussion. î ÄWEATHER STATION Please note that from time to time purveyors of weather/duat make changes in their sequence et al....and do not inform users. These changes require modifications to the command file(s). Data-Plane provides these revisions with subscription service. However if these changes occur mid cycle your weather/duat station will not stay in sync...until the next update. Data-Plane will not be held responsible for these lapses. Please inform us of any changes which you detect. Thank you During modem communication do not interfere or strike any key or respond to any on-screen prompts. The system does not like to be distracted...unless it appears to be permanently hung up waiting for input. 99% of the time <Enter> will restart the process.... Make sure that you call the weather vendor and get a valid log-on Id and password before attempting to communicate. To enter the ID and password strike [F10 / F9] from the Main Menu and request an [U]p-date...and store the up-date to the disc. Make sure that your Log On ID is 9 digits. Type in only the last 6. The program will insert a 'DPI' preface. If you have the modem software and the system hangs-up.......etc. try the following to recover: . [Esc]............[Enter] Occassionally transmission over the modem may become garbled. During the transformation process of Weather to Data-Plane format......the system will start beeping....whenever it finds garbage. The system normally will squawk once or twice....more than that should alert the user to possible bad data. Print the winds aloft...and inspect it. If it looks bad...re-try the modem. Noisy data is rejected by the sysem. ÄPARTIAL DOWNLOADS You may truncate the download by striking...[Esc]...........; as when you only need winds for Canada and don't want the additional information which otherwise would be downloaded. Only a complete winds aloft download from a non-DUAT weather vendor will shut off the "Refresh winds" signal..... ÄWEATHER STATION CAUTIONS It is not a good idea to use "spaces" in a Log-on Id or Password. Some vendors ignore same. Winds aloft are connected to Navaids. If you run a plan that does not pass a navaid....no winds will be reported. Pure lat-lon and airport-to-airport plans will suffer from lack of windage. However this type plan is rare and the weather enroute briefing [F9] will be complete and accurate. From time to time the FAA & NOAA change the names of navaids. Flight plans composed using `stale` data-bases will recieve no data for the new navaids and will see `no data found` for the old navaid name. Keep your data-bases current! Make sure that the winds aloft download was complete. Otherwise you may be composing a flight plan with null winds in several locations. It is good practice to print the `Winds Aloft` to confirm that you have it all. Specific winds will be rejected if the station report is not complete and perfect. It is a good practice to standby during modem operations. Some vendors may not disconnect if their system loses sync or gets hung-up. You won't be happy with your phone bill in that case. Strike [Esc]...........and start over if you suspect trouble. Also apply for a credit with the vendor. The system is designed about 10 minutes for a prompt...which it may never see. If the system halts with an `Error` message....sync has been lost. Strike [Esc]..............and try again....or settle for the data captured up to that point. Make sure you have selected an active COM PORT. From the Wind / Weather Menu strike `*'.....select COM ports 1 - 2. We have run the programs on routes with 90 enroute reporting stations at 1200 and 2400 baud. Beyond that we do not guarantee results. ÄWEATHER STATION NOTES If you have questions regarding the weather call the vendor for interpret- ation and answers. If there is an item which you would like to see in the program call Data-Plane and we'll see what can be done. ÄWIND SCRUB (time dependent) Wind scrub will clear out all winds previously entered. This feature will engage automatically at the following times: 00:00z/ 06:00z/ 12:00z/ 18:00z Also if the winds are over 6 hrs old a message will be flashed to refresh the winds. ÄWIND SCRUB [F9/10]..of Main Menu Wind scrub will clear out all winds previously entered unconditionally by selecting `S` from the `WINDS ALOFT` Menu if not previously done this session. To force a wind scrub escape to DOS...then return to the Weather Menu. This is done to protect you from inadvertently scrubbing good winds. ÄWEATHER After a final flight plan is composed the user may request the weather conditions at all the enroute navaids including airports. This requires the modem feature. Notams will be included if the vendor has them. If not error messages may appear....ignore them. ÄMODEMS Modems should be Hayes compatible. Currently only the COM1-2 ports will be serviced. Both TONE & PULSE telephone systems are supported. Experience to date indicates that a complete download of winds cost abt $2.50 @ 2400 baud. An infinite number of flight plans may be run against this download. Weather enroute reports cost more. ÄTRANSMISSION ERRORS Errors in transmission of data from the weather vendor may occur from time to time. These will be characterized by a lot of noise...or a hang-up with a non-descript error message. Re-do the download...call the vendor and ask for credit. The Winds/Weather Menu is set to std protocols. Sometimes these will not work in the area from which you are dialing. Call the vendor for alternate settings. ÄWINDS ALOFT / WEATHER MENU(s) If you have the weather modem feature the system will fetch current winds aloft from all reporting stations. Thereafter all flight plans will include automatic windage computation if [F5] of the Flight Plan Menu is in the `winds` state. Downloaded winds & those entered manually via this menu will be geographically disbursed....if they are at an NWS 'Reporting Station'...otherwise they are assumed to be unreliable for geographic distribution. The following selections are available: ESC to Exit Exit / Abort any procedure. Enter # to Dial Currently only selections `1 - 9` are active. U Update Entry " A Area Forecast " C Change Colors Affects color(s) of Menu only. S Wind Scrub Scrub winds if not previously done this session. P/T Pulse/Tone Select phone type. *............ Change active COM port (1 or 2 only). M Manual Manually enter winds. V View Winds Aloft W Weather log Print w Winds Aloft Print Prints downloaded winds aloft image. ÄU Update Entry Sub-Menu The following selections are available and preset by Data-Plane. The user may set the following to the specifications of his/her modem. For example the Baud rate is preset to 2400. This may be too fast for your modem. Set the Baud rate to one which is compatible with your modem....etc. As other vendors are added to the list the vendors will supply you with the proper settings. Number to Up-date Only for active vendors. Name Change if not correct for your system. Phone # " Baud Rate " Parity " Data Bits " Stop Bits " Echo On " LogOn ID User must obtain his Log On ID & Password from . weather vendor (e.g. Accu-Weather Inc.) . Log On ID MUST BE 9 digits with the first 3 characters . `DPI`....(type in only the last 6 digits). . Password MUST BE 7 digits. Save to Disk Only changes saved to disk will apply. Note: If vendor does not accept 9 or 7 digits; fill with trailing spaces. . e.g. XXX ,ZZZZZZZ ÄWINDS ALOFT DOWNLOADED IMAGE All modem operations are logged....and may be printed. The image is basically exactly like the data downloaded from a weather vendor. The image/log file is reset before a modem and/or manual operation in preparation for new data. ÄDOWNLOAD TRUNCATION If you determine that you do not want the entire download from a weather vendor...when you see that you have all the winds that you need...e.g. if you do not need Mexican or Canadian winds....strike <esc>..... This will save you $$$$. ÄENTER WINDS MANUALLY This is the preferred comprehensive method of entering winds manually. You may enter winds reported at a Weather Reporting Station....or at any valid Navaid in the data-base. If the entry is a Reporting Station...the winds will be disbursed geographically. This method is effectively an emulation of a download via modem. The effect is the same. It is most useful as a supplement to the Winds Aloft Download. The user may enter winds at selective Navaids not reported elsewhere. The Winds Aloft downloaded image will be not be reset during this operation. Previously dowloaded images will be retained. ÄPHONE NUMBERS Phone numbers are limited to 11 digits (f-aaa-ppp-nnnn)....where f = 1/8/9. Use an 8 or a 9 if you are dialing thru a PBX....such as are found at large companies and motels...eg. 9 - aaa - ppp - nnnn. The system will add a 1 in the proper place. Also 2 Hayes pauses (2 commas) will be added to wait for the second dial tone. Factory settings are expected ( 1.5 sec / comma) for a total pause of 3 seconds. If the local dialout protocol is 9 - ppp - nnnn then no "1" will be inserted. The only problems that may occur have to do with numbers of 11 digits. Call Data-Plane Inc. for custom mods if the sys- tem does work through your PBX. ÄWARNING DO NOT PRESS OR HIT ANY KEY(S) WHILE A MODEM TRANSFER IS IN PROGRESS!!!!!!!!! PATIENCE IS A VIRTUE....REWARDS COME TO THOSE WHO WAIT FOR THE OTHER COMPUTER TO ANSWER THE PHONE. ÄAREA FORECASTS Need only be set once. For example if you fly in the New England area you probably will want the `BOS` area forecast with each briefing. Once set the BOS area forecast will be downloaded with each Weather Enroute report. May be reset at any time. Set separately for each vendor. World Weather Watch (TABS) automatically dowloads the appropriate Forecaste(s). Mention Data-Plane Inc....you will get some free indoctrination time. ÄALARM / AWAKE See published manual for discussion. If you like to sleep in...this function is for you. SET THE ALARM Turn on the computer...the printer....and the modem. Then for example type: _ FBOZ ALARM 2 06:15 PREF *O'HARE *WEST_PALM_BEACH _ FBOZ ALARM 2 06:15.............will only download the winds. _ FBOZ ALARM 2 06:15 RECALL R....will do last plan w/new winds. Rules for the Alarm See published manual for discussion. î ÄSOURCE MATERIAL Ä* NOAA Charts & Maps. * NOAA NAVAID floppy diskettes......collated against current data-base. * DIGITAL SUPPLEMENTS. * FEDERAL REGISTER AMENDMENTS & DELETIONS. * DEPARTMENT OF ENERGY MINES & RESOURCES GOV'T OF CANADA * GREEN RIVER COMMUNITY COLLEGE DEPT OF AVIATION AUBURN WASHINGTON î ============================================================================= DATA-PLANE INCORPORATED 330 S.W. 43rd Street RENTON WA 98055 ============================================================================= 1 - (800) - 323 - 8063 ----------------------------------------------------------------------------- . Program (# = up-dated every 56 days) PRICE _____________________________________________________________________________ # 1.- Clearance(tm) Basic Flight Planner $59.95 # 2.- Automatic Routing & Approach fixes 49.95 . 3.- Weight & Balance (Performance + 50 A/C library + CG graphic) 79.95 # 4.- Airports East w/Runway diagrams 49.95 # 5.- Airports West w/Runway diagrams 49.95 # 6.- Airports Canada & Alaska w/Runway diagrams 49.95 . 7.- tbd # 8.- ATC preferred routes for USA & Canada ATC 49.95 . 9.- Low Altitude Alert for directs (Topographical relief) 39.95 . 10.- Professional Pilot's Log Book (200 yrs) 59.95 . 11.- Dynamic Graphics w/mapping (works on 95% of graphic cards) 49.95 . 12.- Off-Shore Intersections (Atlantic Pacific & Gulf) incl. . 13.- TCA ARSA & Restricted Airspace Alert w/graphing 49.95 # 14.- Airport MASTER w/8700+ airports (Req for AFD's & Diagrams) 49.95 . 15.- tbd . 16.- tbd . 17.- Weather Station (modem software included for Tone/Pulse/PBX) 49.95 . 18.- DUAT interface included with Weather Station incl. . 19.- Airport Pictorials 15 volumes per NOAA plates (3.5inch only) 49.95 ea . 20.- Canadia Pictorials 10 volumes (3.5inch only) 49.95 ea . 21.- STARS (3.5inch only) 49.95 . 22.- SIDS (3.5inch only) 49.95 ============================================================================= SPECIAL PACKAGE -1- $224.95 Includes: Clearance Automatic Chartmaker Graphics City-to-City ATC Preferred Routes Low Altitude Alert Airport Master and Weather / Duat Station(s). SPECIAL PACKAGE -2- $174.95 Includes: Clearance Automatic Airport Master.... and Weather / Duat Station(s). ÄSUBSCRIPTIONS Basic Flight Planner ....$31.97 Other programs/db's......$31.97 Additional copies .......$23.97 (For multiple computers) Airport Master...........$31.97 AFD's & Diagrams.........$31.97 (Airport Master required) Program Enhancements.....$ 0.00 (With Subscription 'Free of Charge') ÄSUBSCRIPTIONS ON HD.....$31.97 w/o Airports & ATC Routes extra. ÄSUBSCRIPTIONS ON HD.....$85.00 w/ Airports. ATC Routes extra. The subscription for each module coincides with the FAA's 56 day up-date cycle...and are non-refundable. Includes: All program improvements and enhancements all approach fixes all off-shore fixes and weather station. . There is a necessity for keeping abreast of changes....and keeping . up-to-date. Data-Plane provides these changes automatically every . 56 days for its subscribers. ÄANNUAL SUBSCRIPTIONS Significant savings can be realized when sub-scriptions are purchased on an annual basis. The annual fee includes S&H. Complete set $ 295.00 + 26.50 s&h _____________________________________________________________________________ HANDLING $ 2.90 per order SHIPPING (As per carrier charge + 10%)........ . 1st class & UPS ground $ 3.90 . 2nd day air 6.25 . Air Letter 12.00 . Air Pak 18.00 . Overnight 31.50 Mastercard & Visa welcome..........also Corporate & Company billing accounts. Washington residents add %8.1 state sales tax. There is a $1.00 non-refundable handling charge per 3 1/2" diskette. _____________________________________________________________________________ ÄLAPTOPS ALTIMA 386SX VGA w/20 megabyte hardrive & 2400 baud modem/fax Notebook with 17 software modules and DOS 4.01............. $call ALTIMA 386SX VGA w/120 megabyte hardrive & 2400 baud modem/fax Laptop w/17 software modules and DOS 4.01.................... $call ALTIMA 286 VGA w/40 megabyte hardrive & 2400 baud modem/fax (3.5" inches thick) with 17 software modules and DOS 4.01..... $call KODAK Diconix printer for laptops (retail $500+)............... $call Subscribers receive rebate equal to one cycle payment. î ÄGEnie * If you are a member of the GEnie Network you may download copies of any programs or their corresponding up-dates and your account will be charged automatically. This is the fastest method of delivery. The Data-Plane programs are available in the AVIATION RT <lib 16 & 17>. * Also the AVIATION Bulletin Board has two(2) categories 21 & 22 dedicated exclusively to Data-Plane Inc. These Bulletin Boards will allow you to comm- unicate with other pilot-users....and with Data-Plane directly. If you are a member of GEnie call Data-Plane Inc. and let us know your E-MAIL or UP-LOADER address. (We don't want your Password). It will be entered into a `private file` for use of Category 22...and give you access to lib <17>. * To be successfully invited you must visit Category 21 at least once every 30 days. ÄEDI NETWORK 1-800-776-6076 EDI is on the Minitel Net Info-Look in (Boston and New York) Community Link (Omoha NB) Bell Atlantic (Washington DC area) & Bell South (Atlanta). EDI will be on-line with BT TYMNET accessable in 20 countries and 850 cities by calling the TYMNET local number and typing "software" from the logon prompt. Type `GO AVIATOR` for the Data-Plane Forum. ----------------------------------------------------------------------------- ÄDISKETTE SERIAL NUMBERS Serial numbers should not be relied upon. Insert the diskette into either floppy drive....and type: _ TYPE IDENTIFY [Enter] This will reveal which is the latest diskette. î ÄPILOT LOG BOOK * Hard-copy reports may be used for Insurance qualification...and TAXES. * The Pilot Log book is a spread sheet type program which allows 20 different sub-field entries......covering all the known hourly break-downs; in addition to 6 descriptive fields....and will maintain 200 yearly totals. * Three (3) additional sub-fields are present for keeping expense records i.e. FUEL $ MISC $ & MAINTENANCE $ / RENTAL $. These costs are maintained in (+) or (-) form(s) so that the user may apply refunds or fees to his bookkeeping. These 3 fields are summed on the hard copy so that the user is supplied with 1) Total cost per trip 2) Year-to-date cost(s) & 3) Cost per hour. * All sub-field titles are user defined. * 20 sub-totals are computed...including a grand total of "Total Time". * Reports may be generated & collated on Make & Model and/or Tail No. * It is possible to create 2 to the 20th power (alot) sub-totals and reports times the number of sub-type A/C for which you keep records. * It is extremely easy to use....and the legend of active keys are constantly displayed on the screen. All editing functions are present...including Insert a line or delete a line and many more. * Hard copy print-outs are included. * The log book will hold a life-time of flight time delineated into years. * A new Log Book allows variable length fields of 1 - 4 columns for any given year...and is compatible with prior versions. Customize your Log. * This module may be installed with the CLEARANCE system or operated separate- ly as a single floppy system. * The built in flexibility allows the log book to used by a pilot; and also to be applied an aircraft log. Handy for keeping track of costs per a/c. î ÄTROUBLE? *.-Modules not installed will fail to execute if requested by user. 1.-Check your hard-disc for available memory and error conditions (CHKDSK). Fix your hard-disc before attempting to load this software. 2.-Check your DOS set-up. Many DOS systems are not properly set-up. Check the following DOS procedures especially: _ VER / PATH / see DOS discussion below. 3.-Do not attempt to modify or interfere with the Install procedures. The system is self loading and self starting and will set up its own directories. 4.-Data-Plane Inc. has gone to great lengths to reduce the dependency on a hard copy manual. The system is user ready. However because of the scope size and flexibility of this system users sometimes experience difficulty attempting to go beyond their current knowledge of navigation. It is recommended that you stay within your limits until such time as you feel comfortable with the system. You will eventually learn more about navigation from this program than any other source and you will enjoy the process more if you don't rush. Bear in mind that this system serves the purposes of airline operators....as well as students. 5.-Printer should be in EPSOM compatible pure text mode....Check dip switches! _ The Epson (fx) character set & control codes are employed for printing. _ e.g. (Dot Matrix) EPSOM/ IBM/ CITIZEN/ PANASONIC/ BLUE CHIP/ TOSHIBA/ NEC. * LAZER etc. printers require an EPSOM emulator. We recommend `LazerControl' _ by Insight Developments of San Francisco...1-800-825-4115. Daisy wheel _ printers like DIABLO & QUME may also be operated by `LazerControl`. _ Mention Data-Plane and you will receive a discount. * Graphic screen print-outs require a graphics printer. * 24pin printers (LQ) work only in the 60 dpi mode. 6.-An illegal function call may occur if your graphics set-up is switched to a _ non-standard mode. Check for switches. Also if other devices are connected _ to graphics card....they invariably must be on-line & in `ready state'. 7.-Adjust the brightness & contrast if the cursor is not visible. 8.-Enter way-points in CAPS.....only some Canadian & private airports require _ small letters. 9.-Attempting to call a procedure or module not installed will invariably _ result in a default to the MAIN Menu. 10.-Erasing a file may cause a system crash or other problem. Data-Plane _ assumes no liability if files are erased. Otherwise the system is _ `crash-proof` and the user should not be timid. 11.-CHECK [Num-Lock] for CORRECT POS. 12.-WEATHER STATION software has been run w/DOS 3.1 & better. Please report _ problems to Data-Plane immediately. Currently the Weather station requires _ an operational `SHELL` statement....which is resident in your DOS command _ file. Your system may hang if you attempt to access a COM PORT which does _ not exist in your system. Reset your computer and modem. Also try another _ BAUD rate....or switch to Pulse dialing if you experience trouble. _ Also your modem cannot share a line with any other user e.g. a FAX which _ might try to dial out in the middle of a comm. 13.-The basic Flight Planner requires 3.5 megs of available hard disc space. 14.-A complete system requires about 8.5 megs of available space on the hard _ disc. And the system grows with use. One pilot-user has reported a system _ of 12 megs. Make sure you have enough room before proceeding to install. _ Frequently visit the Audit section via [F8] of the Main Menu to clean out _ unnecessary routes. 15.-Some versions of DOS will not inform the user that there is not sufficient _ room available on the hard disc for a load. Be alert to this possibility. _ It may cause a 'null' file to be created. 16.-Those alleged $20 `surge` protectors will not cut it. A surge in the line _ has been known to pick off a bit or a byte. Get a good one. 17.-`No link` and `Unable to locate` messages may appear when the station ID _ has been changed.....or an Airway has been shut down. The AUTOMATIC will _ suggest routes through areas which the FAA has temporarily shut down. _ Check with your local FSS and edit the plan. This same condition occurs _ when an Airport ID has been changed. Plans which may have run OK before _ may start to fail when the FAA NOAA or the Canadians make changes. _ Check your data-bases...it's easy...that is what they are there for. 18.-Another common problem occurs when the user attempts to install a new _ module....run with an old version of the flight planner. Make sure your _ programs are up-to-date. 19.-Runways become outdated with each new issue of a corresponding AFD. You _ must up-date the runways to keep them compatible with the AFD(s). 20.-Each time you install the Clearance Flight Planner diskette the system _ will attempt to print the Copyright Notice via the DOS PRINT module. _ If you do not allow the printing to occur the system will overload the _ DOS PRINT buffer. Type PRINT /T.....to clear this buffer. 21.-Respond to prompts in kind as to upper/lower case. Users have reported _ hung systems when in fact the system is waiting for the proper lower / _ upper case response. 22.-Some users have thought the system was hung when in fact all was running. _ The Main Menu has a clock in the upper right hand corner which will _ confirm life. 23.-Graphic selections are dubious at best. Continue to experiment until you _ identify the one which works best with your system. Chartmaker graphics _ tests your graphics set-up...and does away with the need to repeat the _ selection. 24.-To test if specific data-bases have been loaded correctly....from the _ Main Menu select: _ [F4] for Navaids [F5] for Intersections [F6] for Airports. _ If you get spurrious results then the data-base is not loaded. There are _ many diskettes and users sometimes forget to install all. 25.-It is a good idea to print the `Winds Aloft` file from the Weather Menu _ to ascertain that a complete download occurred i.e. one that was not _ aborted etc. Specific winds will be rejected if they are not perfect. 26.-The Weight & Balance program should be operated with the printer on. 27.-Try as we might...sometimes the Canadians or Mexicans or NOS slip us a _ duplicate intersection name. For example `WHITE` appeared in both Canada _ and the US at the same time....2000 nm apart. The system registers the _ first one it encounters...which may be the wrong one. Always check the _ lat-lon of all fixes to see if they have resolved to the intended place. _ It is easy to spot the spurrious ones. To fix select [F5] from the Main _ Menu...and correct. It's rare...but it does happen....and its obvious _ when it does. Be sure to let us know. 28.-Airways only link at Navaids or published Intersections. 29.-If the system is requesting a DME Fix for an element that it does not _ recognize....Press <enter> if you want to abort. 30.-Occassionally a message e.g. `SBN missing` may appear....although SBN _ is not in the plan. This occurs when an intersection off of SBN is used _ and SBN does not exist any more. This is a mistake in the database. SBN _ should have been changed to GIJ. Please call Data-Plane and let us know. _ To fix: return to Main Menu and select [F5]. Type the name of the _ intersection. E.g. `PLAIN`. Correct and return to Flight Planning. 31.-City to City Routes which are not part of the database at any given _ moment will not play....Audit & Search reveal the presense of a Route. 32.-Magnetic courses over long segments are unreliable. Fly TO the 'Fix' _ or navaid. 33.-Any error will kill automatic batch processing in progress and revert _ to manual mode. 34.-You must have the latest programs for DOS INTEGRATORS to work. 35.-Tail Numbers must match exactly where applicable. 36.-Batch mode processing (DOS Integrators) will switch to manual if an error _ is detected. However printing operations will wait for a return to DOS. 37.-The accuracy of the graphed charts depends to a large extent on the data supplied by NOAA & DEM&R. We have found large errors in surveyed magnetic variations surveyed radials & dme distances. Therefore sometimes a lat-lon is resolved to a position not agreeing with the book. This is also caused by great distances used in the fix....which nullifies the radial after a point. Users are cautioned not to fly legs over 99 miles without a fix. 38.-Fuel burn analysis will not occur unless the Tail number of the current aircraft=Tail number of the aircraft loaded via "quick load" or W&B. Likewise...Option -G- will not prompt for fuel load if the Tail numbers do not match. 39.-Airports defined in lower case do not transfer/id very well as DOS converts these to upper case. The airport is there but the id is not properly transferred. However Chartmaker does understand the difference between cases and will respond correctly. 40.-"Illegal function....." may result in some graphic mode selections. This is most likely caused by a lack of space in your computer. Select another mode. 41.-The path via AFD's to Clearance is unreliable....but correct. It may select random planner options or graph a random airport when charting. Neither aberration is fatal. This path often returns directly to DOS. 42.-Canadian Intersections may have two nearby positions (lat-lon) depending on what kind of an airway they are on (Victor/Jet or NDB). Please check. 43.-'TOO LONG / PARTITION' usually may be corrected by supplying as many airway connections as there is room for. Use the [Ins] key for this purpose. 44.-If you attempt to chart a route which has a segment length of zero... it will fail. It is not fatal. Users should obtain the pertinent LOW or HIGH ENROUTE IFR Charts before attempting to use this system. Knowledge of the ATC system is very helpful. If you have difficulties understanding the out-put it is helpful to take it to your instructor who will go over it with you. ÄQUESTIONS????......... DATA-PLANE INC HOT LINE: (206) 838 - 4181. The hot line is a call interrupt system. If busy it switches to voice mail. î ÄDOS * COMMAND.COM AUTOEXEC.BAT & CONFIG.SYS must be in the root directory. * If you experience difficulties.....check CONFIG.SYS file of DOS. Hard disc systems should have at least BUFFERS = 24 & FILES = 24. Many systems as delivered do not have a BUFFERS command and the default is 10. * To accommodate systems which have defective CONFIG.SYS files all Clearance programs attempt to set BUFFERS = 28 & FILES = 24. Many users will notice a marked improvement in the performance of their systems. Others may want to reduce or increase the above. Use the DOS SET command. * Also DEVICE = ANSI.SYS & LASTDRIVE = F should be part of CONFIG.SYS file. * Check if your system requires the FCBS command. * PATH=C:\DOS;C:\ (or a facsimile should be in your AUTOEXEC.BAT file) * If you have reason to change CONFIG.SYS and/or AUTOEXEC.BAT turn your computer off.........then on. All of your software will run faster. * If you have 3.5 inch disk drives the following command should appear in your CONFIG.SYS file for each 3.5 inch (720k) drive: _ DRIVPARM = /D:d where d = 0 for drive A & d = 1 for drive B * Make sure that your DOS has all its programs loaded....and that there is a PATH to the DOS. Especially look for PRINT & SORT. If they are not present certain important performances will be passed over....causing the user to think that the software is in error....when in fact it has called for a DOS module which did not exist in your set-up during the install. Therefore a `Clearance` module may not load...and when called for by program interaction will fault. DOS does not give clear indications of problems in many cases. There are usually two (2) disks for a DOS version....load both. * Users of DOS 3.20 may need a STACKS command. There is a bug in DOS 3.20 (eliminated in 3.21 ob) that involves what are known as stack pointers. The bug may produce a system crash. Happily simply adding the line STACKS=64128 to your CONFIG.SYS file will swat that worrisome bug. Don't forget to shut off your computer once a change has been made to the CONFIG.SYS file. * Modem operations may fail when the vendor changes his menu & command file. Please let Data-Plane know about this. They are reviewed every 56 days. Also each vendor has quirks. Learn them...and try to avoid pitfalls. Some quirks are easily fixed by manual intervention....with the system kicking back into the automatic mode. However Alarm functions may fail due to these quirks and changes. î